Logic arrangement, system and method for configuration and control in fieldbus applications

ABSTRACT

The present invention relates generally to a logic arrangement, system and method which aid in a design of a fieldbus network configuration. In particular, the present invention includes certain functions for an automatic generation and verification of block and device tags, function block verification and modifications for function block type consistency based on information in the block profile, automatic allocation of function blocks into devices by an off-line scheduler, and a control strategy configuration system (which uses artificial intelligence to generate and maintain a fieldbus design knowledge-base). Accordingly, the user is able to easily configure the fieldbus network and devices residing thereon in an effective manner, as well as use the previously used configurations for establishing new fieldbus networks.

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from U.S. application Ser. No.60/412,236, filed Sep. 20, 2002, the entire disclosure of which isincorporated herein by reference.

FIELD OF THE INVENTION

[0002] The present invention relates generally to a logic arrangement,system and method which aids in configuring and controlling componentson a fieldbus network. In particular, the present invention providescapabilities for automatic generation and verification of function blocktags, device tags, and function block type consistency based oninformation in the block profile. The present invention also allows foran automatic allocation of the function blocks for the field devices byan off-line scheduler, and provides a control strategy configurationsystem and process which uses artificial intelligence techniques and/orarrangements to generate and maintain a fieldbus design knowledge-base.

BACKGROUND OF THE INVENTION

[0003] Process control systems and methods provide a way for improvingefficiency, reliability, profitability, quality and safety in aprocess/product manufacturing environment. Such process control systemsand methods can be used for automation, monitoring and control ofdevices and applications in a wide array of industrial applications formany industry segments, such as textiles, glass, pulp and paper, mining,building, power, sugar, food and beverage, oil and gas, steel, water andwastewater, chemicals, etc.

[0004] Conventional process control systems and methods generallyoperate with a plurality of field devices positioned at variouslocations on, e.g., a 4-20 mA analog network. These field devicesinclude measurement and control devices (such as temperature sensors,pressure sensors, flow rate sensors, control valves, switches, etc., orcombinations thereof). Recently, a number of protocols have beenintroduced which provide a digital alternative to conventional controlsystems and methods, and which utilize “smart” field devices. These“smart” field devices can provide the same functionality as theconventional devices listed above, and may additionally include one ormore microprocessors, one or more memories, and/or other componentsincorporated therein. Such smart field devices can be communicativelycoupled to each other and/or to a central processor using an open smartcommunications protocol. Such protocol (e.g. Foundation® Fieldbusprotocol) has been widely used in manufacturing and process plants. Anumber of such protocols have been developed for non-process controlenvironments, such as automobile manufacturing or building automation,and then later adapted to be used for process control. Some of the morewidely used fieldbus protocols include Hart®, Profibus®, Foundation®Fieldbus, Controller Area Network protocols, etc.

[0005] Fieldbus process control systems and methods may also utilize acontroller that is communicatively coupled to each of the smart fielddevices using an open “smart” communications protocol, and a servercommunicatively coupled to the controller using, for example, anEthernet connection. Moreover, this controller may include a processor,and can receive data from each of the “smart” field devices. Such“smart” field devices each preferably include a processor for performingcertain functions thereon, without the need to use the central host forperforming such functions. The amount of processing to be executed bythe centralized host generally depends on the type of the controlapplication and the protocol used.

[0006] A smart fieldbus device, as configured by a softwareconfiguration tool, may be programmed to execute function blocks. Afunction block can provide fundamental automation functions that areperformed by the process control application. In essence, the functionblocks are software models which can define the behavior of the processcontrol system. More particularly, the function block may be a softwarelogic unit which processes input parameters according to a specifiedalgorithm technique and an internal set of control parameters, andgenerates resulting output parameters that are available for use withinthe same function block application and/or by other function blockapplications. The input parameters of one function block may be linkedto the output parameters of one or more other function blocks on thefieldbus network. The execution of each function block can be scheduled.After the function block is executed using the corresponding inputvalues, its outputs are updated and then published on the network, wherethey can be subscribed by inputs of other function blocks using thisinformation. These linked function blocks may reside either inside thesame field device or in different devices on the network.

[0007] Three different types of function blocks are generally used inthe fieldbus applications, e.g., Resource Blocks, Function Blocks, andTransducer Blocks. For example, the Resource Blocks define parametersthat pertain to the entire application process inside a device (e.g.,manufacturing ID, device type, etc.). The Function Blocks encapsulatecontrol functions (e.g., PID controller, analog input, etc.). TheTransducer Blocks represent an interface to sensors such as temperature,pressure and flow sensors.

[0008] Each function block in the system can be identified by a uniquetag which is generally assigned by the user. The parameters of eachfunction block can be represented by object descriptions that define howthe parameters are communicated on the fieldbus network. Thus, manyparameters in the system are likely uniquely identified by theirreference to their block tag and parameter name or, alternatively, bytheir reference to their block tag and parameter relative index (theordinal index that represents the offset of the parameter in the wholelist of parameters).

[0009] Each fieldbus device likely has a Resource Block and at least oneFunction Block with input and/or output parameters that link to otherfunction blocks, either in the same device or in separate devices byusing the fieldbus. Each input/output parameter generally includes aparticular value portion and a particular status portion. The statusportion of each parameter includes information regarding the reliabilityof the data contained in the input/output parameter, and instructs thereceiving function block as to whether the reliability of contained datais acceptable, uncertain or unacceptable. In addition, a Function BlockApplication Process (“FBAP”) can specify the handling of control modes,alarms, events, trend reports and views. These features comply with theFoundation® specification in order for the device to be consideredinteroperable at a User Layer.

[0010] Distribution of control to the field devices can be performed bysynchronizing the execution of the function block, and transmitting thefunction block parameters on the fieldbus network. Such functions, alongwith the publication of the “time of day” to the devices, an automaticswitch over to a redundant time publisher, an automatic assignment ofdevice addresses, and a search for parameter names or “tags” on thefieldbus can generally be handled by System Management and/or NetworkManagement.

[0011] A control strategy may be generated through an interconnection ofthe various function blocks contained in the field devices. The controlstrategy may also be modified without any hardware changes, thusproviding another level of flexibility. Function blocks and controlstrategies are further described in the Foundation® Fieldbus andProfibus® fieldbus specifications, both of which are incorporated hereinby reference.

[0012] The configuration of a fieldbus control strategy, however, can bean extremely complex task. A large application can involve hundreds oreven thousands of function blocks. Such a large fieldbus networkconfiguration may have several associated problems. The manual typing ofblock tags can be extremely repetitive, time consuming and cumbersome.Additionally, the manual entry of block tag names may result in errors.It may also be a waste of resources for a trained technician to spend asignificant amount of time entering the tag names.

[0013] Further, conventional software configurators are usually complexand unwieldy due to the open nature of known fieldbus network protocols.Such configurators are designed to accommodate devices produced by anumber of different vendors which may provide a wide variety offunctionality. Many of these configurators (in an effort to simplifytheir design) generally rely on a scheme in which the configuration isloaded directly from the field devices. However, it may be advantageousto provide for the configuration to be completed and modified off-lineas well.

[0014] Additionally, because of the high level of complexity of fieldbuscontrol strategies, prior art software configurators may need a highlytrained user with substantial fieldbus experience to perform allconfiguration creation and modification functions.

[0015] Currently, there exists no logic arrangement, system and methodwhich can automatically generate function block tags based on the devicetag for the device containing the function block. Such logicarrangement, system and method would facilitate a more efficientconfiguration procedure for a fieldbus network and devices.Additionally, there exists no logic arrangement, system and method whichcan be configured to maintain the consistency of function block tags insuch scheme, whereby the function block may be moved from one device toanother, and therefore (due to this deficiency) the tag would thereforeneed to be manually changed to remain consistent with the tag namingscheme. Furthermore, there exists no logic arrangement, system andmethod which facilitate off-line scheduling of function blocks andnetwork traffic for a fieldbus network while automatically distributingfunction blocks to the devices.

SUMMARY OF THE INVENTION

[0016] Therefore, a need has arisen to provide a logic arrangement,system and method of the present invention which automatically generatesblock tags based on either the device tag for the device containing theblock or the control strategy tag for the control strategy containingthe block. Such a logic arrangement, system and method may facilitate amore efficient configuration procedure for a fieldbus network.Additionally, an exemplary software system used by the logicarrangement, system and method of the present invention can beconfigured to ensure a consistency of function block tags. In thisexemplary scheme for naming or tagging the function block where thefunction block tag names are based on particular device tags (orparticular control strategy tags), the function blocks may be moved fromone device to another (or from one control strategy to another), and thetag can be automatically updated by the logic arrangement system andmethod to maintain consistency with the tag naming scheme. Furthermore,the logic arrangement, system and method of the present invention mayfacilitate off-line scheduling of the function blocks and networktraffic for providing a fieldbus network control strategy configuration.Moreover, the software system used by the logic arrangement, system andmethod of the present invention may provide an automated assistance forconfiguring a control strategy for the fieldbus network.

[0017] One of the advantages of the logic arrangement, system and methodaccording to the present invention is that it can increase theefficiency with which the user can design a fieldbus applicationconfiguration comprising many fieldbus network segments. Further, theconfiguration and scheduling functions may be performed off-line,without the need for a complete physical fieldbus network installation.Another advantage of the logic arrangement, system and method accordingto the present invention is that they may allow a less experienced userto configure a fieldbus network due to the fact that many of the taskscan be automated. Additionally, the logic arrangement, system and methodof the present invention may provide information to the user so as toguide the user in configuring the fieldbus network.

[0018] One exemplary embodiment of the logic arrangement, system, andmethod for configuring a fieldbus network according to the presentinvention can obtain particular information relevant to a function blockand automatically generating a tag for the function block. According toanother exemplary embodiment, it is possible to determine whether a typeof a particular function block is supported by a device that is capableof being connected to the fieldbus network, and executes at least oneoperation based on such determination.

[0019] At least one template containing predefined fieldbusconfiguration data can be obtained, and a configuration for the fieldbusnetwork may be generated based on such template(s). In another exemplaryembodiment of the present invention instructional information associatedwith a configuration of the fieldbus network can be generated based onthe template(s).

[0020] Furthermore, it is possible to obtain information regarding thetype of application for a fieldbus network control, record the obtainedinformation in a storage arrangement, and generate the fieldbusconfiguration information based on the information provided in thestorage arrangement.

[0021] According to yet another exemplary embodiment of the presentinvention certain data associated with the fieldbus network can beobtained, such data including at least one function block, at least oneparameter and information regarding at least one device which is capableof being coupled to the fieldbus network. Then, execution of suchfunction block(s) can be scheduled in the device(s) and at least oneparameter may be published to the fieldbus network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] For a more complete understanding of the present invention, theneeds satisfied thereby, and the objects, features, and advantagesthereof, reference now is made to the following descriptions taken inconnection with the accompanying drawings.

[0023]FIG. 1 shows an exemplary embodiment of a system according to thepresent invention.

[0024]FIG. 2 is a sample screenshot generated by an exemplary embodimentof software used by the logic arrangement, system and method of thepresent invention for providing an automatic generation of functionblock tags, with the context being a global context.

[0025]FIG. 3 is a sample screenshot generated by another exemplaryembodiment of the software used by the logic arrangement, system andmethod of the present invention, in which the context is a devicecontext.

[0026]FIG. 4 is a sample screenshot generated by an exemplary embodimentof the software used by the logic arrangement, system and method of thepresent invention, in which the context is a control module context.

[0027]FIG. 5 is a flow diagram for an exemplary embodiment of the methodaccording to the present invention provided for an automatic generationof function block tags.

[0028]FIG. 6 is a flow diagram of an exemplary embodiment of the methodaccording to the present invention provided for determining whether afunction block type is supported by a particular device.

[0029]FIG. 7 is a sample screenshot generated by the exemplary softwareof the present invention for maintaining function block-type consistencyby comparing the supported function block with the function block to beassociated with the particular device.

[0030]FIG. 8 is another sample screenshot generated by the software ofthe present invention.

[0031]FIG. 9 is yet another sample screenshot generated by the softwareof the present invention.

[0032]FIG. 10 is a sample screenshot generated by an exemplaryembodiment of software assistant according to the present invention,showing a window for selecting a strategy template, and providing a tagname therefor.

[0033]FIG. 11 is a sample screenshot generated by the exemplary softwareassistant which shows a window for selecting device templates.

[0034]FIG. 12 is a sample screenshot generated by the exemplary softwareassistant which shows a window for associating input/output functionblocks with transducer channels.

[0035]FIG. 13 shows a diagram of scheduled processes for a fieldbusnetwork control strategy with converging branches generated by anexemplary embodiment of the logic arrangement, system and methodaccording to the present invention.

[0036]FIG. 14 shows a diagram of scheduled processes for a fieldbusnetwork control strategy with diverging branches generated by theexemplary embodiment of the logic arrangement, system and methodaccording to the present invention.

[0037]FIG. 15 shows a diagram of scheduled processes for a fieldbusnetwork control strategy with parallel paths generated by the exemplaryembodiment of the logic arrangement, system and method according to thepresent invention.

[0038]FIG. 16 shows a diagram of scheduled processes for a fieldbusnetwork control strategy with a feedback path generated by the exemplaryembodiment of the logic arrangement, system and method according to thepresent invention.

[0039]FIG. 17 shows an exemplary fieldbus network device containing twofunction blocks which are linked within the device using the logicarrangement, system and/or method according to the present invention.

DETAILED DESCRIPTION

[0040] Exemplary embodiments of the present invention and theiradvantages may be understood at least by referring to FIGS. 1-17, likenumerals being used for like corresponding parts in the variousdrawings.

[0041]FIG. 1 shows an exemplary embodiment of a fieldbus network systemwith which the logic arrangement, system and method of the presentinvention may be utilized. A computer apparatus 10 may be connected to afieldbus network 16 via an interface apparatus 12 (e.g., a FieldbusNetwork Interface). The computer apparatus 10 may be a personal computerthat includes a processor and memory, and can also be connected to adatabase and/or to a computer network. The fieldbus network 16 may haveattached thereto one or more fieldbus devices 14. The computer apparatus10 may execute software according to the present invention for providingand/or modifying a configuration of the fieldbus network system whichmay include, among other elements, the fieldbus network 16 and thefieldbus devices 14.

[0042]FIG. 2 is a sample screenshot generated by software and/orhardware as used by an exemplary embodiment of the logic arrangement,system and method for automatically generating a fieldbus block tagaccording to the present invention. A screen 20 may contain thereon afieldbus network segment configuration window 22, which may display ahierarchy of a fieldbus configuration. This exemplary embodiment of thelogic arrangement, system and method may first determine the context ofthe block. The software according to the present invention may generateunique block tag names, e.g., based on the context of the particulardevice and/or block.

[0043] The screen 20 provides a display for an automatic generation oftags, where the selected context for the block tag names can be “Global”context. According to this exemplary embodiment, blocks 24 within suchtag generation context can be named as follows: Block1, Block2, . . .BlockN, where N is the total number of blocks in the complete fieldbusconfiguration.

[0044]FIG. 3 shows another sample screenshot generated by thesoftware/hardware used by the exemplary embodiment of the logicarrangement, system and method according to the present invention. On ascreen 30, the selected context can be “Device” context. In thisexemplary embodiment, the block tag names may be generated based on thename of the particular device to which the block is allocated. Afieldbus network segment configuration window 32 may contain a device 34named TIC101. The tag names that may be generated for blocks 36 that arebased, at least in part, on the name of the device 34 to which theblocks are allocated. According to the exemplary embodiment generatingthe window 32 of FIG. 3, the tag naming convention is such that a blocktag name can be based on the following format:

<device_name>_<block-type-mnemonic>

[0045] where the parameter <device_name> is the name of the device 34,and the parameter <block-type-mnemonic> may be defined by the type offunction block, e.g., AI1 for the first generated analog input block,AI2 for the next generated analog input block, PID1 for the firstgenerated PID control function block, etc. The separator selected toseparate the various parameters in the tag name may be an underscorecharacter for this exemplary embodiment; however, it should beunderstood that any number of characters may be used as a separator (ornone at all) depending upon the particular implementation and/or thechoice of a human user.

[0046]FIG. 4 shows yet another sample screenshot generated by thesoftware/hardware of the exemplary embodiment of the logic arrangement,system and method according to the present invention. On a screen 40,the selected context is a control module context. In this exemplaryembodiment, the function block tag names may be generated based on thename of the particular control module to which the function block isallocated. A process cell configuration window 42 may contain a controlmodule 44 named FIC200. The tag names that can be generated for functionblocks 46 based, at least in part, on the name of the control module 44to which the function blocks 46 are allocated. According to theembodiment of the present invention generating the window 42 of FIG. 4,the tag naming convention is such that a function block tag name isbased on the following format:

<controlmodule_name>_<block-type-mnemonic>

[0047] where the parameter <controlmodule_name> can be the name of thecontrol module 44, and the parameter <block-type-mnemonic> may bedefined as provided above by the type of function block, e.g., All forthe first generated analog input block, AI2 for the next generatedanalog input block, PID1 for the first generated PID control functionblock, etc. The separator that may be selected to separate the variousparameters in the tag name can be a hyphen character for this exemplaryembodiment.

[0048] The exemplary embodiment of the software used to automaticallygenerate fieldbus function block tags according to the present inventioncan define additional contexts. One additional context may be apredefined default context. A predetermined format may be establishedfor a default tag, which can be based on a scheme similar to thosedescribed above. In addition, the context may be based on the class ofthe function block. According to one exemplary embodiment of thisdefault tag name generation scheme, resource blocks and transducerblocks may have a device context, while function blocks may have acontrol module context. One reason for such a distinction is thataccording to their definitions in the Foundation Fieldbusspecifications, resource blocks and transducer blocks can be intimatelyrelated to the hardware of the particular device, while function blocksare basic building blocks of control modules. Different default taggeneration formats may also be used.

[0049]FIG. 5 shows an exemplary embodiment of a method according to thepresent invention for automatically generating the function block tags.The exemplary method may first determine whether the context is a devicecontext in step 52, and/or if the context is a strategy context in step53. If neither context is selected, the method may then automaticallycreate a tag based on a default scheme in step 58. However, if thecontext is a device context, the method may then determine if the blockis attached to a device in step 54. If the block is attached to a devicethen a device tag is available and the function block tag may begenerated based on that device tag (step 56). Otherwise, a default tagmay be generated in step 58. If the context is a strategy context, instep 55, it is possible to verify whether a strategy tag is currentlyavailable. If the strategy has a particular tag, the function block tagis automatically generated based on the strategy in step tag 57.Otherwise, the function block may then be named based on the defaultnaming scheme in step 58. In step 59, the tag can be generated.

[0050] In another exemplary embodiment of an automatic fieldbus functionblock tag generation software (or hardware) according to the presentinvention, the logic arrangement, system and method may be implementedto maintain the consistency of the block tags when the function blocksare moved within the configuration such that their context changes. Forexample, in one exemplary fieldbus network configuration, the context isa device context, and an analog input function block may, e.g., have atag name “TIC101_AI1.” If the function block is then moved from thedevice TIC101 to a device TIC202, a new tag “TIC202_AI1” may begenerated for the analog input function block so as to maintain theconsistency of the naming convention. Similar operations may also beperformed to maintain consistency where the context is control module,global, default, or some other context.

[0051] Further, if the context itself is changed in the configuration,rather than moving the function block, the exemplary embodiment of thelogic arrangement, system and method of the present invention maymaintain consistency of the function block tag names by generating newtags so as to match the new context. For example, in one exemplaryconfiguration, the context of a configuration can be a device context,and the configuration may contain an analog input function block withthe current tag of, e.g., “TIC101_AI1.” If the context itself is changedto the control module context, the exemplary embodiment of the logicarrangement, system and method may automatically generate a new tag forthis function block, e.g., “FIC100_AI1.” Similarly, if the tag of thecontext changes, the block tags that are dependent on that context willfollow the change to remain consistent. Various other modifications ofthese naming rules and conventions may also be implemented.

[0052] Numerous other situations may arise where the logic arrangement,system and method of the present invention may attempt to generate a newtag for the function block, but the tag may not be available, e.g., whenthe context, is a device context but the function block is not yetattached to any device. In such cases, the logic arrangement, system andmethod may generate a default to be a different context for purposes ofgenerating a temporary tag name, and can additionally include anotherdesignation in the tag so as to indicate that the current tag wascreated as a “placeholder,” e.g., a different separator than theselected separator may be used, etc.

[0053] In another exemplary embodiment of the present invention, thelogic arrangement, system and method may be implemented for ensuring aconsistent allocation of function block types into the appropriatedevices. For example, when the user attempts to allocate a functionblock to a particular device in a fieldbus network configuration, thelogic arrangement, system and method of the present invention maydetermine whether the type of function block is supported by theparticular field device. Standard parameters defined in thespecification for the fieldbus network protocol may be used to performthe verification. In one exemplary embodiment of the present invention(as implemented for the use with a Foundation Fieldbus network), thefollowing standard parameters may be used to perform the verification:Manufacturer code, Profile, ProfileRevision, DDIdentification andDDItemId. Based on the parameters (with the number of parameters checkedvarying with the particular implementation of the present invention),the logic arrangement, system and method can determine the type of thefunction block. The function block types may include a “Standard” block,the parameters of which are explicitly defined in the FoundationFieldbus specification; an “Enhanced” block, which is a standard blockextended by appending proprietary parameters at the end of the block; a“Custom” block, a proprietary block definition whose parameter set isfully defined by the manufacturer; and an “Enhanced Custom” block, whichis a custom block extended by appending proprietary parameters at theend of the block.

[0054] The types of function blocks that may be supported by aparticular device can be found in that device's Capabilities File anddescribed in that device's Device Description (DD) as defined in theFoundation Fieldbus specification. The logic arrangement, system andmethod can therefore match the type of the function block that is beingadded to the device with the device's supported function block types. Ifthe function block type is supported by the device, then the functionblock may be added to the device. Otherwise, the operation may beaborted, and/or additional steps may be performed to conform thefunction block to operate with the particular device.

[0055] One exemplary embodiment of a method for checking block typeconsistency according to the present invention is shown in FIG. 6. Inparticular, steps 62, 64, 66 and 68 may be used to determine whether allthe requirements for block-type consistency are met. The requirements inthis exemplary embodiment of the method are that the Profile of at leastone of the supported block types should match the Profile of the blockto be attached (step 62), the enhancement number of the available blocktype matches the enhancement number of the block to be attached or theattached block is not an enhanced block (step 64), the block to beattached is neither a custom block nor an enhanced block or if the blockto be attached is one of these types, then the manufacturer of thedevice is the same as the manufacturer of the block to be attached (step66), and the DD of the block to be attached should be different fromthat in the device or if the DD is same then the DDItemId of a supportedblock type should match the DDItemId of the block to be attached (step68). If all of these requirements are met, then it is determined thatthe block may be added to the particular device in step 69. However, ifany of these criteria are not met, it is determined that the block isnot supported (step 67).

[0056] Upon the determination that a particular function block is notsupported by a device, several exemplary actions may be performed,depending on the implementation of the logic arrangement, system andmethod of the present invention. The logic arrangement, system andmethod may simply abort the operation, and generate a warning message.Alternatively, the logic arrangement, system and method may allow forthe function block to be reconciled with the supported function blocktypes of the device so that it can still be attached. The manner inwhich the function block may be reconciled can vary depending on theimplementation. In one exemplary embodiment of the present invention,the following reconciliation rules may generally apply (these rules mayvary depending on the particular implementation): Block can be attachedto a device if the device supports an enhanced version of that type ofblock. Enhanced block can be added to a device if the device supports anon-enhanced version of that type of block only if the user is warnedabout the loss of information and accepts it. The common parameterswould not be checked. The parameters of enhanced part of the blocks maybe lost. Enhanced block can be added to a device if the device supportsa different enhancement of the same base block type only if the user iswarned about the loss of information and accepts it. The commonparameters would not be checked. The parameters of enhanced part of theblocks would be compared for association, automatically or uponinstructions from the user, and the user may confirm the changes. Blockcan be added to a device that does not support either that block type oran enhancement version of it provided that the user chooses a base blocktype and reconciles the parameters individually. For resource blocks inparticular, because the resource block for Interoperability Test Kit(ITK) 4.0 is an enhancement of the previous ordinary resource blockdefinition, the following rules may apply: Ordinary resource block canbe attached to a device that supports a resource block for ITK 4.0 butthe block type (the Profile) should change to reflect the operation.Resource block for ITK 4.0 can be attached to a device that supports anordinary resource block but the block type (the Profile) must change toreflect the operation, and the user should be warned about the loss ofinformation.

[0057] In another exemplary embodiment of the logic arrangement, systemand method according to the present invention for ensuring theconsistent allocation of function block types into the appropriatedevices (where a particular function block is not supported by thedevice), a user-assistant may be invoked to aid the user in identifyingand resolving inconsistencies so as to force the attachment of thefunction block to the device. FIG. 7 shows a sample screenshot generatedby an exemplary software implemented according to the present invention.A window depicted in FIG. 7 illustrates a visual representation of theparameters analyzed in the consistency check. A foreign block type 70 ofthe window represents the function block which the logic arrangement,system and method are attempting to attach to the device, and includes aManufacturer number 71, a Profile number 72, a Profile Revision 73, andparameters 74. A native block type 75 is one of the block typessupported by the device to which the function block is being attached,and includes Manufacturer number 76, a Profile number 77, a ProfileRevision 78, and parameters 79. As shown in the parameter lists 74 and79, the foreign function block type 70 can be compatible with the devicebecause the supported native function block type is an enhanced block,while the foreign block is a standard block. All of the parameters 74 ofthe foreign block 70 may be contained in the native block 75. However,the additional parameters of native block 75, which are not included inthe foreign block 70 may be configured before the function block, can beattached to the device. These parameters may be displayed in a differentcolor, or identified in some other manner as a status indication to theuser.

[0058] The exemplary embodiment of the software used by the logicarrangement, system and method of the present invention shows a samplescreenshot in FIG. 8 for a comparison of a foreign block of enhancedtype as compared to a device supporting a standard block type. In thisexemplary illustration, a foreign block type 80 includes parameters 82,and a native block type 84 includes other parameters 86. Because theforeign block type 80 includes certain parameters which are notcontained in the native block type 84, these parameters may be clippedout or removed in order to allow for the function block to be attachedto the device. These additional parameters may be shown in a differentcolor or marked differently in some other way, as they are marked with,e.g., a strikethrough in FIG. 8.

[0059] The exemplary embodiment of the software used by the logicarrangement, system and method of the present invention shows anothersample screenshot in FIG. 9 for a comparison when the foreign block typeand the native block type are both of an enhanced type, but are fromdifferent manufacturers. The foreign block type 90 includes parameters92, and the native block type 94 includes other parameters 96. Eachblock type contains the parameters which are not contained by the otherblock type. The logic arrangement, system and method of the presentinvention may handle this scenario in numerous ways, including alertingthe user to the mismatched parameters, obtaining confirmation from theuser to clip out unsupported parameters, etc.

[0060] As indicated above, the parameters displayed in the displays andwindows may be shown in various colors or formats to alert the user asto their status. In one exemplary embodiment, a parameter that has nomatch in the native block (and will be clipped out) may be shown in redwith a strikethrough, a parameter that has no match in the foreign block(but is contained in the native block) may be shown in green, a foreignparameter which has the same name and structure (but different basictype as that in the native parameter such that it will match under atype conversion) may be shown in yellow, etc. In addition, the user canforce the comparison and matching of the parameters which may not bematched by the logic arrangement, system and method because they mayhave different names. Likewise, the user can disassociate parametersthat are automatically associated together by the logic arrangement,system and method of the present invention. The user can performadditional functions, such as defining values, etc. Indeed, the user maybe allowed to intervene and override some or all steps of thereconciliation process.

[0061] A reconciliation template may be implemented in the exemplaryembodiment of the present invention for maintaining block typeconsistency. Rather than displaying to the user the interface for everysingle function block in the reconciliation process, a template may beutilized to automatically process same or all function blocks in aparticular batch in a substantially similar manner. A log may begenerated during the batch processing such that the user may be informedregarding any inconsistencies that were encountered during thereconciliation process.

[0062] In another exemplary embodiment of the present invention, thelogic arrangement, system and method may be implemented for providing afieldbus configuration generation assistant. Such assistant may beimplemented using software and/or hardware, and can include databasecapabilities for storing various information regarding fieldbus networkconfigurations such as complete configurations, templates, informationrelated to devices and other fieldbus components, etc. Thesoftware/hardware may automate steps of the fieldbus networkconfiguration process, and may provide information and templates to theuser so as to aid the user in configuring the fieldbus network.Additionally, the user may provide information regarding the needs ofthe fieldbus network, the type of application (pasteurization, flowcontrol, chemical process, etc.) and additional information, and theassistant according to the present invention may provide the fieldbusconfiguration based on the information stored in a knowledge base keptin a database, storage device and/or elsewhere. In this manner, the userwould only need to have limited knowledge of the fieldbus networks inorder to configure such fieldbus network.

[0063]FIG. 10 shows a first sample screenshot generated by an exemplaryembodiment of the logic arrangement, system and method of the presentinvention. As illustrated in FIG. 10, a window 100 may be displayed tothe user so as to aid the user in selecting a template for a controlstrategy in an exemplary fieldbus network configuration. The window 100may include control strategy template information 102 regarding aparticular control strategy template, and a control strategy diagram 104which may provide information about the control strategy, such as thecontained function blocks, links between the function blocks, attachmentto devices, etc. The logic arrangement, system and method may alsoprovide additional information to the user so as to aid the user inselecting, e.g., the best strategy template for the application.

[0064]FIG. 11 shows the next sample screenshot generated by theexemplary embodiment of the logic arrangement, system and method. Awindow 110 of FIG. 11 may be displayed to the user to also aid such userin selecting a template for a particular device in a fieldbus networkconfiguration (as with the window 100 of FIG. 10). A window 110 mayinclude information regarding one or more device templates 112. The usermay select particular devices by selecting a corresponding devicetemplate from the window 110 to be used in the fieldbus networkconfiguration. The logic arrangement, system and method can provideinformation to the user to aid the user in selecting the devices.Additionally, the user can define device tags for each deviceindividually.

[0065]FIG. 12 shows yet another successive sample screenshot of anexemplary embodiment of the logic arrangement, system and method. Awindow 120 of FIG. 12 may be displayed to the user to assist the user inassociating input/output function blocks with transducer channels withinthe particular device. A window 120 may include information 122regarding the input/output (I/O) function block channel parameters andavailable transducer function block channels. The user may associate theI/O function blocks shown in window 120 with particular transducer blockchannels in the device.

[0066] Based on the information provided by the user in the screens ofFIGS. 10-12, the configuration assistant according to the presentinvention may complete the configuration of the fieldbus network byautomatically instantiating some or all of the necessary or preferredfunction blocks, assigning tags to the function blocks, instantiatingsome or all of the function block links in the strategy, instantiatingthe devices by utilizing a device template, assigning the tags to eachdevice, instantiating the resource block and transducer blocks in eachdevice, assigning the tags to the resource blocks and transducer blocks,assigning each function block to its respective device, and connectingthe channel of the I/O function blocks to the corresponding transducerblock channels. This exemplary procedure of the present inventioneffectively automates some or all of the configuration process.Depending on the implementation of the present invention, differenttypes of information may be collected from the user, and different stepsof the configuration process may be automated by the configurationassistant. The generation of tags for the blocks may use any one of theautomatic block tag generation schemes already mentioned and one furthermethod is possible when dealing with block templates. The tags can bebased on block aliases provided in the templates in substitution toblock mnemonic. If the selected context is a device context, thestructure of the tag may be as follows:

<device_name>_<block-alias-in-template>

[0067] where the parameter <device_name> is the name of the device. Ifthe selected context is a control module context, the structure of thetag may be as follows:

<controlmodule_name>_<block-alias-in-template>

[0068] where the parameter <controlmodule_name> can be the name of thecontrol module. The block alias is a short tag for the block in thestrategy template and may refer to the role of the block in thestrategy.

[0069] In another exemplary embodiment of the present invention, thelogic arrangement, system and method may be implemented for the off-linescheduling of function block execution and network traffic. The logicarrangement, system and method may utilize a scheduling algorithm whichis known in the art, such as the algorithm disclosed by Jia Xu in“Multiprocessor Scheduling of Processes with Release Times, Deadlines,Precedence, and Exclusion Relations,” (IEEE Transactions on SoftwareEngineering, Vol. 19, No. 2, February 1993, pp. 139-54) and disclosed byXu and David Parnas in “Scheduling Processes with Release Times,Deadlines, Precedence, and Exclusion Relations,” (IEEE Transactions onSoftware Engineering, Vol. 16, No. 3, March 1990, pp. 360-9), bothincorporated herein by reference. The scheduling arrangement and methodaccording to the present invention can schedule function blockapplication processes, which includes the execution of function blocksin the devices and the publishing of output parameters to the fieldbusnetwork (in accordance with a scheduling algorithm), and additionallymay be configured to distribute the function blocks to the fieldbusdevices. Some or all of the scheduling functions may be performedoff-line, e.g., without the need for a connection to a physical fieldbusnetwork installation. Indeed, the scheduling functions may also beperformed prior to the physical installation of the fieldbus network,thus providing an opportunity to analyze scheduling issues prior to thephysical implementation of the fieldbus network. The control strategiespreferably contain some or all of the information that may be requiredto perform the scheduling functions off-line, e.g., the micro-cycles andmacro-cycles, function blocks and their corresponding links, theassignment of function blocks to devices, the nature of links betweenthe function blocks (i.e., internal, within a particular device, orexternal to the devices, between different devices), precedencerelations among the tasks, exclusion relations among the tasks, etc.

[0070] The scheduling arrangement and method of the present inventionmay be configured to implement a schedule for numerous different typesof control strategies, which may be utilized on a particular segment ofthe fieldbus network. For example, as shown in FIG. 13, a controlstrategy for a particular network branch may involve convergingbranches. Exemplary processes 130 may all converge and provide inputdata to process 132. The scheduling arrangement and method of thepresent invention may be configured to ensure that the scheduling of thevarious processes coincides such that a process 132 is not executeduntil the converging processes 130 are completed. As shown in FIG. 14,the scheduling arrangement and method of the present invention may alsobe configured to properly schedule processes in the fieldbus networksegment where diverging paths are utilized. For example, a process 140diverges, and provides inputs to multiple diverging processes 142. Othercases may similarly be handled where the processes 150, 152 operate inparallel paths, as shown in FIG. 15, and when processes 160, 162 operatewith feedback paths, as shown in FIG. 16. The scheduling arrangement andmethod of the present invention may be configured to ensure that aparameter publishing can be synchronized with the execution of thefunction blocks, e.g., output parameters shall be published to thefieldbus network after the block it belongs to executes, and an inputparameter is published before such execution of the block to which itbelongs. Additionally, the scheduling arrangement and method may verifythat there are no ambiguities in block-execution precedence, identifyfeedback loops in the control strategy, and can be configured to satisfycertain restrictions that are created by limits on available resources.In these ways, the scheduling arrangement and method of the presentinvention may ensure a proper operation of the processes in accordancewith the provided control strategy.

[0071] Additionally, the scheduling arrangement and method may allow forthe control strategies in the same fieldbus network segment to havedifferent micro-cycles, make provision for the time used for fieldbusnetwork traffic supervision, and further verify a central processingunit (CPU) available time so as to ensure efficient operation of theschedule.

[0072] The scheduling arrangement and method may also allocate theoutput parameters to the link active schedule (“LAS”) processor of thefieldbus network. The LAS processor is preferably the component whichcontrols the scheduling of traffic on the fieldbus. This may bepreferable in certain applications, because the output parameters mayalways be published to the network, and thus they may have to beallocated to the LAS processor in order to effectuate proper networkoperation in accordance with the fieldbus protocol.

[0073] Further, the scheduling arrangement and method according to anexemplary embodiment of the present invention may also ensure the properallocation of the function blocks to the devices. In particular, I/Ofunction blocks generally are executed in the same device as theirassociated transducer block. This is due to the fact that they areconnected by a channel internal to the fieldbus device. Accordingly, thescheduling arrangement and method of the present invention may beconfigured to ensure that the function blocks are distributed to thedevices such that this relationship is maintained, i.e., I/O functionblocks may be allocated to the same devices as their respectivetransducer blocks.

[0074] As shown in FIG. 17, an exemplary device 174 may contain theinput/output function block 172 and the transducer block 176. As thescheduling arrangement and method allocate function blocks to variousdevices in this exemplary fieldbus network configuration, they can alsoarrange that the blocks 172, 176 are allocated to the same device, sincethe connection between such blocks is likely internal to the samedevice. Similar rules can be implemented to ensure consistency andproper configuration of the fieldbus network.

[0075] Additionally, the scheduler may also be configured to determinewhether a particular device to which the block is being allocated is ofthe proper type such that the device supports the function block (asdescribed herein above), and whether the particular device to which theblock is being allocated has sufficient available resources such that itcan properly operate according to the function block rules and/orrequirement. These resources may include memory, object dictionaryentries, block execution schedule entries, etc.

[0076] While the invention has been described in connection withpreferred embodiments, it will be understood by those of ordinary skillin the art that other variations and modifications of the preferredembodiments described above may be made without departing from the scopeof the invention. Other embodiments will be apparent to those ofordinary skill in the art from a consideration of the specification orpractice of the invention disclosed herein. It is intended that thespecification and the described examples are considered as exemplaryonly, with the true scope and spirit of the invention indicated by thefollowing claims.

What is claimed is:
 1. A logic arrangement for configuring a fieldbusnetwork, which, when executed by a processing arrangement, is operableto perform steps comprising of: obtaining particular informationrelevant to a function block; and automatically generating a tag for thefunction block.
 2. The logic arrangement of claim 1, wherein thegeneration of the tag is performed based on the particular information.3. The logic arrangement of claim 2, wherein the particular informationincludes a context of the function block.
 4. The logic arrangement ofclaim 3, wherein the context of the function block is at least one of aglobal-relevant context, a device-relevant context, a controlmodule-relevant context and a default context.
 5. The logic arrangementof claim 3, wherein, when executed by a processing arrangement, thelogic arrangement is further operable to perform the steps of:determining whether the particular information of the function blockchanged; and if a change of the particular information is detected,generating a further tag for the function block based on a furthercontext of the further tag.
 6. A method for configuring a fieldbusnetwork, comprising the steps of: obtaining particular informationrelevant to a function block; and automatically generating a tag for thefunction block.
 7. The method of claim 6, wherein the generation of thetag is performed based on the particular information.
 8. The method ofclaim 7, wherein the particular information includes a context of thefunction block.
 9. The method of claim 8, wherein the context of thefunction block is at least one of a global-relevant context, adevice-relevant context, a control module-relevant context and a defaultcontext.
 10. The method of claim 7, further comprising the steps of:determining whether the particular context information of the functionblock changed; and if a change of the particular information isdetected, generating a further tag for the function block based on afurther context of the further tag.
 11. A system for configuring afieldbus network, comprising: a processing arrangement operable toexecute the following instructions: obtaining particular informationrelevant to a function block, and automatically generating a tag for thefunction block.
 12. The system of claim 11, wherein the generation ofthe tag is performed based on the particular information.
 13. The systemof claim 12, wherein the particular information includes a context ofthe function block.
 14. The system of claim 13, wherein the context ofthe function block is at least one of a global-relevant context, adevice-relevant context, a control module-relevant context and a defaultcontext.
 15. The system of claim 12, wherein the processing arrangementis further operable to perform the following instructions: determiningwhether the particular information of the function block changed; and ifa change of the particular information is detected, generating a furthertag for the function block based on a further context of the furthertag.
 16. A logic arrangement for configuring a fieldbus network, which,when executed by a processing arrangement, is operable to perform stepscomprising of: determining whether a type of a particular function blockis supported by a device which is capable of being connected to thefieldbus network; and executing at least one operation based on thedetermination.
 17. The logic arrangement of claim 16, wherein the atleast one operation includes a generation of an indication that theparticular function block is not supported by the device.
 18. The logicarrangement of claim 16, wherein the at least one operation includes atermination of at least one further operation.
 19. The logic arrangementof claim 16, wherein the at least one operation includes a substitutionof a first type of the particular function block which is not supportedby the device with a second type of a further function block which issupported by the device, and wherein the first and second types aredifferent from one another.
 20. The logic arrangement of claim 19,wherein the at least one operation includes a duplication of informationfrom the particular function block to the further function block. 21.The logic arrangement of claim 19, wherein the at least one operationincludes a modification of information of at least one of the particularfunction block and the further function block.
 22. The logic arrangementof claim 16, wherein the type of the particular function block is atleast one of a standard block, an enhanced block, a custom block and anenhanced custom block.
 23. The logic arrangement of claim 19, whereinthe type of the particular function block is at least one of a standardblock, an enhanced block, a custom block and an enhanced custom blockand wherein the type of the further function block is at least one of afurther standard block, a further enhanced block, a further custom blockand a further enhanced custom block.
 24. A method for configuring afieldbus network, comprising the steps of: determining whether a type ofa particular function block is supported by a device which is capable ofbeing connected to the fieldbus network; and executing at least oneoperation based on the determination.
 25. The method of claim 24,wherein the at least one operation includes generation of an indicationthat the type of the particular function block is not supported by thedevice.
 26. The method of claim 24, wherein the at least one operationincludes a termination of at least one further operation.
 27. The methodof claim 24, wherein the at least one operation includes a substitutionof a first type of the particular function block which is not supportedby the device with a second type of a further function block which issupported by the device, and wherein the first and second types aredifferent from one another.
 28. The method of claim 27, wherein the atleast one operation includes a duplication of information from theparticular function block to the further function block.
 29. The methodof claim 27, wherein the at least one operation includes a modificationof information of at least one of the particular function block and thefurther function block.
 30. The method of claim 24, wherein the type ofthe particular function block is at least one of a standard block, anenhanced block, a custom block and an enhanced custom block.
 31. Themethod of claim 27, wherein the type of the particular function block isat least one of a standard block, an enhanced block, a custom block, andan enhanced custom block, and wherein the type of the further functionblock is at least one of a further standard block, a further enhancedblock, a further custom block and a further enhanced custom block.
 32. Asystem for configuring a fieldbus network, comprising: a processingarrangement operable to execute the following instructions: determinewhether a type of a particular function block is supported by a devicewhich is capable of being connected to the fieldbus network, and executeat least one operation based on the determination.
 33. The system ofclaim 32, wherein the at least one operation includes generation of anindication that the type of the particular function block is notsupported by the device.
 34. The system of claim 32, wherein the atleast one operation includes a termination of at least one furtheroperation.
 35. The system of claim 32, wherein the at least oneoperation includes a substitution of a first type of the particularfunction block which is not supported by the device with a second typeof a further function block which is supported by the device, andwherein the first and second types are different from one another. 36.The system of claim 35, wherein the at least one operation includes aduplication of information from the particular function block to afurther function block of a different type.
 37. The system of claim 35,wherein the at least one operation includes a modification ofinformation of at least one of the particular function block and thefurther function block.
 38. The system of claim 32, wherein the type ofthe particular function block is at least one of a standard block, anenhanced block, a custom block and an enhanced custom block.
 39. Thesystem of claim 35, wherein the type of the particular function block isat least one of a standard block, an enhanced block, a custom block, andan enhanced custom block, and wherein the type of the further functionblock is at least one of a further standard block, a further enhancedblock, a further custom block and a further enhanced custom block.
 40. Alogic arrangement for configuring a fieldbus network, which, whenexecuted by a processing arrangement, is operable to perform stepscomprising of: obtaining at least one template containing predefinedfieldbus configuration data; and generating a configuration for thefieldbus network based on the at least one template.
 41. The logicarrangement of claim 40, wherein the fieldbus configuration dataincludes data for at least one function block.
 42. The logic arrangementof claim 41, wherein the data for the at least one function blockcontains at least one parameter.
 43. The logic arrangement of claim 40,wherein the fieldbus configuration data includes data for at least twofunction blocks which are linked to one another.
 44. The logicarrangement of claim 43, wherein the data for the at least one of thefunction blocks contains at least one parameter.
 45. The logicarrangement of claim 40, wherein the fieldbus configuration dataincludes data for a resource block.
 46. The logic arrangement of claim45, wherein the data for the at least one resource block contains atleast one parameter.
 47. The logic arrangement of claim 40, wherein thefieldbus configuration data includes data for a transducer block. 48.The logic arrangement of claim 47, wherein the data for the at least onetransducer block contains at least one parameter.
 49. The logicarrangement of claim 40, wherein the at least one template is a strategytemplate.
 50. The logic arrangement of claim 49, wherein, when executedby the processing arrangement, the logic arrangement is further operableto automatically instantiate at least one function block withparameterization.
 51. The logic arrangement of claim 49, wherein, whenexecuted by the processing arrangement, the logic arrangement is furtheroperable to automatically instantiate at least one link to a functionblock.
 52. The logic arrangement of claim 50, wherein, when executed bythe processing arrangement, the logic arrangement is further operable toautomatically assign a tag to the at least one function block.
 53. Thelogic arrangement of claim 40, wherein the at least one template is adevice template.
 54. The logic arrangement of claim 53, wherein, whenexecuted by the processing arrangement, the logic arrangement is furtheroperable to automatically instantiate at least one device.
 55. The logicarrangement of claim 54, wherein, when executed by the processingarrangement, the logic arrangement is further operable to automaticallyassign a tag to the at least one device.
 56. The logic arrangement ofclaim 54, wherein, when executed by the processing arrangement, thelogic arrangement is further operable to automatically instantiate atleast one resource block in the at least one device.
 57. The logicarrangement of claim 56, wherein, when executed by the processingarrangement, the logic arrangement is further operable to automaticallyassign a tag to the at least one resource block.
 58. The logicarrangement of claim 54, wherein, when executed by the processingarrangement, the logic arrangement is further operable to automaticallyinstantiate at least one transducer block in the at least one device.59. The logic arrangement of claim 58, wherein, when executed by theprocessing arrangement, the logic arrangement is further operable toautomatically assign a tag to the at least one transducer block.
 60. Thelogic arrangement of claim 58, wherein, when executed by the processingarrangement, the logic arrangement is further operable to automaticallyconnect the at least one transducer block to at least one channel of aninput/output function block.
 61. The logic arrangement of claim 58,wherein, when executed by the processing arrangement, the logicarrangement is further operable to automatically assign at least onefunction block to at least one device connectable to the fieldbusnetwork.
 62. A logic arrangement for configuring a fieldbus network,which, when executed by a processing arrangement, is operable to performsteps comprising of: obtaining at least one template containingpredefined fieldbus configuration data; and generating instructionalinformation associated with a configuration of the fieldbus networkbased on the at least one template.
 63. A logic arrangement forconfiguring a fieldbus network, which, when executed by a processingarrangement, is operable to perform steps comprising of: obtaininginformation regarding a type of an application for fieldbus networkcontrol; recording the obtained information in a storage arrangement;and generating fieldbus configuration information based on theinformation provided in the storage arrangement.
 64. The logicarrangement of claim 63, wherein the information stored in the storagearrangement includes data regarding an equipment used at a manufacturingplant.
 65. The logic arrangement of claim 63, wherein the type ofapplication includes at least one of a particular field of manufactureand an industrial process.
 66. The logic arrangement of claim 63,wherein the fieldbus configuration information includes at least one ofa design rule, a typical device type, information related toconfiguration of the fieldbus network and control strategy data.
 67. Amethod for configuring a fieldbus network, comprising the steps of:obtaining at least one template containing predefined fieldbusconfiguration data; and generating a configuration for the fieldbusnetwork based on the at least one template.
 68. The method of claim 67,wherein the fieldbus configuration data includes data for at least onefunction block.
 69. The method of claim 68, wherein the data for the atleast one function block contains at least one parameter.
 70. The methodof claim 68, wherein the fieldbus configuration data includes data forat least two function blocks which are linked to one another.
 71. Themethod of claim 70, wherein the data for the at least one of thefunction blocks contains at least one parameter.
 72. The method of claim67, wherein the fieldbus configuration data includes data for a resourceblock.
 73. The method of claim 73, wherein the data for the at least oneresource block contains at least one parameter.
 74. The method of claim67, wherein the fieldbus configuration data includes data for atransducer block.
 75. The method of claim 74, wherein the data for theat least one transducer block contains at least one parameter.
 76. Themethod of claim 67, wherein the at least one template is a strategytemplate.
 77. The method of claim 76, further comprising the step ofautomatically instantiating at least one function block.
 78. The methodof claim 76, further comprising the step of automatically instantiatingat least one link to a function block.
 79. The method of claim 77,further comprising the step of automatically assigning a tag to the atleast one function block.
 80. The method of claim 67, wherein the atleast one template is a device template.
 81. The method of claim 80,further comprising the step of automatically instantiating at least onedevice.
 82. The method of claim 81, further comprising the step ofautomatically assigning a tag to the at least one device.
 83. The methodof claim 81, further comprising the step of automatically instantiatingat least one resource block in the at least one device.
 84. The methodof claim 83, further comprising the step of automatically assigning atag to the at least one resource block.
 85. The method of claim 81,further comprising the step of automatically instantiating at least onetransducer block in the at least one device.
 86. The method of claim 85,further comprising the step of automatically assigning a tag to the atleast one transducer block.
 87. The method of claim 85, furthercomprising the step of automatically connecting the at least onetransducer block to at least one channel of an input/output functionblock.
 88. The method of claim 85, further comprising the step ofautomatically assigning at least one function block to at least onedevice connectable to the fieldbus network.
 89. A method for configuringa fieldbus network, comprising the steps of: obtaining at least onetemplate containing predefined fieldbus configuration data; andgenerating instructional information associated with a configuration ofthe fieldbus network based on the at least one template.
 90. A methodfor configuring a fieldbus network, comprising the steps of: obtaininginformation regarding a type of an application for fieldbus networkcontrol; recording the obtained information in a storage arrangement;and generating fieldbus configuration information based on theinformation provided in the storage arrangement.
 91. The method of claim90, wherein the information stored in the storage arrangement includesdata regarding an equipment used at a manufacturing plant.
 92. Themethod of claim 90, wherein the type of application includes at leastone of a particular field of manufacture and an industrial process. 93.The method of claim 90, wherein the fieldbus configuration informationincludes at least one of a design rule, a typical device type,information related to configuration of the fieldbus network and controlstrategy data.
 94. A system for configuring a fieldbus network,comprising: a processing arrangement operable to execute the followinginstructions: obtain at least one template containing predefinedfieldbus configuration data; and generate a configuration for thefieldbus network based on the at least one template.
 95. The system ofclaim 94, wherein the fieldbus configuration data includes data for atleast one function block.
 96. The system of claim 95, wherein data forthe at least one function block contains at least one parameter.
 97. Thesystem of claim 94, wherein the fieldbus configuration data includesdata for at least two function blocks which are linked to one another.98. The system of claim 97, wherein the data for the at least one of thefunction blocks contains at least one parameter.
 99. The system of claim94, wherein the fieldbus configuration data includes data for a resourceblock.
 100. The system of claim 99, wherein the data for the at leastone resource block contains at least one parameter.
 101. The system ofclaim 94, wherein the fieldbus configuration data includes data for atransducer block.
 102. The system of claim 101, wherein the data for theat least one transducer\block contains at least one parameter.
 103. Thesystem of claim 94, wherein the at least one template is a strategytemplate.
 104. The system of claim 103, wherein the processingarrangement is further operable to automatically instantiate at leastone function block.
 105. The system of claim 103, wherein the processingarrangement is further operable to automatically instantiate at leastone link between two or more function blocks.
 106. The system of claim104, wherein the processing arrangement is further operable toautomatically assign a tag to the at least one function block.
 107. Thesystem of claim 94, wherein the at least one template is a devicetemplate.
 108. The system of claim 107, wherein the processingarrangement is further operable to automatically instantiate at leastone device.
 109. The system of claim 107, wherein the processingarrangement is further operable to automatically assign a tag to the atleast one device.
 110. The system of claim 107, wherein the processingarrangement is further operable to automatically instantiate at leastone resource block in the at least one device.
 111. The system of claim110, wherein the processing arrangement is further operable toautomatically assign a tag to the at least one resource block.
 112. Thesystem of claim 108, wherein the processing arrangement is furtheroperable to automatically instantiate at least one transducer block inthe at least one device.
 113. The system of claim 112, wherein theprocessing arrangement is further operable to automatically assign a tagto the at least one transducer block.
 114. The system of claim 112,wherein the processing arrangement is further operable to automaticallyconnect the at least one transducer block to at least one channel of aninput/output function block.
 115. The system of claim 112, wherein theprocessing arrangement is further operable to automatically assign atleast one function block to at least one device connectable to thefieldbus network.
 116. A system for configuring a fieldbus network,comprising: a processing arrangement operable to execute the followinginstructions: obtain at least one template containing predefinedfieldbus configuration data; and generate instructional informationassociated with a configuration of the fieldbus network based on the atleast one template.
 117. A system for configuring a fieldbus network,comprising: a processing arrangement operable to execute the followinginstructions: obtain information regarding a type of an application forfieldbus network control, record the obtained information in a storagearrangement, and generate fieldbus configuration information based onthe information provided in the storage arrangement.
 118. The system ofclaim 117, wherein the information stored in the storage arrangementincludes data regarding an equipment used at a manufacturing plant. 119.The system of claim 117, wherein the type of application includes atleast one of a particular field of manufacture and an industrialprocess.
 120. The system of claim 117, wherein the fieldbusconfiguration information includes at least one of a design rule, atypical device type, information related to configuration of thefieldbus network and control strategy data.
 121. A logic arrangement forconfiguring a fieldbus network, which, when executed by a processingarrangement, is operable to perform steps comprising of: obtaining dataassociated with the fieldbus network, the data including at least onefunction block, at least one output parameter and information regardingat least one device which is capable of being coupled to the fieldbusnetwork; and scheduling an execution of the at least one function blockin or by the at least one device and a transmission of at least oneoutput parameter to the fieldbus network.
 122. The logic arrangement ofclaim 121, wherein during the scheduling step, the at least one functionblock is allocated to the at least one device.
 123. The logicarrangement of claim 121, wherein during the scheduling step, at leastone output parameter is allocated to a link active schedule processorfor the fieldbus network.
 124. The logic arrangement of claim 121,wherein, when executed by the processing arrangement, the logicarrangement is operable to determine whether the at least one functionblock is connected to at least one further block within a same device bya link internal to the same device, and if the at least one functionblock is connected to the at least one further block by a link internalto the same device, operable to allocate the at least one function blockand the at least one further block to the same device.
 125. The logicarrangement of claim 124, wherein the at least one function block is aninput/output function block, wherein the link is a channel internal tothe same device and at least one further block is a transducer block.126. The logic arrangement of claim 122, wherein the at least onefunction block is capable of being allocated to the at least one deviceonly if the at least one device supports the particular type of the atleast one function block.
 127. The logic arrangement of claim 122,wherein the at least one function block is capable of being allocated tothe at least one device only if the at least one device has sufficientresources for the allocation of the at least one function block. 128.The logic arrangement of claim 127, wherein the resources include atleast one of memory, an object-dictionary entry and a block executionschedule entry.
 129. The logic arrangement of claim 121, wherein thescheduling is performed off-line.
 130. A method for configuring afieldbus network, comprising the steps of: obtaining data associatedwith the fieldbus network, the data including at least one functionblock, at least one output parameter and information regarding at leastone device which is capable of being coupled to the fieldbus network;and scheduling an execution of the at least one function block in the atleast one device and a transmission of at least one output parameter tothe fieldbus network.
 131. The method of claim 130, wherein during thescheduling step, the at least one function block is allocated to the atleast one device.
 132. The method of claim 130, wherein during thescheduling step, at least one output parameter is allocated to a linkactive schedule processor for the fieldbus network.
 133. The method ofclaim 130, further comprising the steps of: determining whether the atleast one function block is connected to at least one further blockwithin a same device by a link internal to the same device; and if theat least one function block is connected to the at least one furtherblock by a link internal to the same device, allocating the at least onefunction block and the at least one further block to the same device.134. The method of claim 131, wherein the at least one function block isan input/output function block, wherein the link is a channel internalto the same device and the at least one further block is a transducerblock.
 135. The method of claim 130, wherein the at least one functionblock is capable of being allocated to the at least one device only ifthe at least one device supports the particular type of the at least onefunction block.
 136. The method of claim 132, wherein the at least onefunction block is capable of being allocated to the at least one deviceonly if the at least one device has sufficient resources for theallocation of the at least one function block.
 137. The method of claim136, wherein the resources include at least one of a memory, anobject-dictionary entry and a block execution schedule entry.
 138. Themethod of claim 130, wherein the scheduling is performed off-line. 139.A system for configuring a fieldbus network, comprising: a processingarrangement operable to execute the following instructions: obtain dataassociated with the fieldbus network, the data including at least onefunction block, at least one output parameter, and information regardingat least one device which is capable of being coupled to the fieldbusnetwork; and schedule an execution of the at least one function block inthe at least one device and a publishing of at least one outputparameter to the fieldbus network.
 140. The system of claim 139, whereinduring the scheduling step, the at least one function block is allocatedto the at least one device.
 141. The system of claim 139, wherein duringthe scheduling step, at least one output parameter is allocated to alink active schedule processor for the fieldbus network.
 142. The systemof claim 139, wherein the processing arrangement is further operable to:determine whether the at least one function block is connected to atleast one further block within a same device by a link internal to thesame device, and if the at least one function block is connected to theat least one further block by a link internal to the same device,allocate the at least one function block and the at least one furtherblock to the same device.
 143. The system of claim 142, wherein the atleast one function block is an input/output function block, wherein thelink is a channel internal to the same device and the at least onefurther block is a transducer block.
 144. The system of claim 140,wherein the at least one function block is capable of being allocated tothe at least one device only if the at least one device supports theparticular type of the at least one function block.
 145. The system ofclaim 140, wherein the at least one function block is capable of beingallocated to the at least one device only if the at least one device hassufficient resources for the allocation of the at least one functionblock.
 146. The system of claim 145, wherein the resources include atleast one of a memory, an object-dictionary entry and a block executionschedule entry.
 147. The system of claim 121, wherein the scheduling isperformed off-line.